Skip to main content

This is a new service – your feedback will help us to improve it.

Tewkesbury Borough Council

Tree preservation zone

There is a problem

  • 435 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Highnam Court Highnam Gloucester Gloucestershire GL2 8HZ

reference
A7-197GCC-MIXED
name
Highnam Court Highnam Gloucester Gloucestershire GL2 8HZ
tree-preservation-order

undefined

https://tewkesburybc.s3.eu-west-2.amazonaws.com/tpos/TPO197_Highnam_Ct_Highnam.pdf
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.302843 51.872638,-2.302812 51.872370,-2.302764 51.872352,-2.302648 51.872382,-2.302504 51.872413,-2.302407 51.872413,-2.302167 51.872425,-2.302022 51.872414,-2.301925 51.872402,-2.301512 51.872475,-2.301462 51.872236,-2.301250 51.872267,-2.300576 51.872358,-2.300528 51.872436,-2.300481 51.872489,-2.299999 51.872479,-2.300048 51.872568,-2.300019 51.872675,-2.299904 51.872777,-2.300031 51.872914,-2.300561 51.872925,-2.300609 51.872924,-2.300744 51.872972,-2.300706 51.873061,-2.300726 51.873103,-2.300966 51.873073,-2.301206 51.872851,-2.301543 51.872892,-2.301902 51.873160,-2.302007 51.873052,-2.302151 51.873040,-2.302170 51.872968,-2.302295 51.872920,-2.302392 51.872938,-2.302431 51.873009,-2.302671 51.872949,-2.302698 51.872710,-2.302765 51.872639,-2.302843 51.872638)))
point
POINT (-2.301412 51.872677)
notes
entry-date
2004-09-09
start-date
2004-09-09
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

This diagram shows the relationship between the tree preservation order dataset and the tree preservation zone dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree preservation zone dataset.

How to improve Tewkesbury Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL